Miro Audit Logs (Enterprise Plan)
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊
| Attribute | Value |
|---|---|
| Connector ID | MiroAuditLogsDataConnector |
| Publisher | Miro |
| Used in Solutions | Miro |
| Collection Method | CCF |
| Connector Definition Files | MiroAuditLogs_DataConnectorDefinition.json |
| CCF Configuration | MiroAuditLogs_PollingConfig.json |
| CCF Capabilities | APIKey, Paging |
The Miro Audit Logs data connector enables you to ingest organization-wide audit events from Miro into Microsoft Sentinel. Monitor user activities, security events, content access, team changes, and administrative actions to enhance your security operations and compliance capabilities.
Key features:
-
Track user authentication and access patterns.
-
Monitor content creation, sharing, and deletion.
-
Audit team and organization configuration changes.
-
Detect suspicious activities and policy violations.
-
Meet compliance and regulatory requirements.
Requirements:
-
Miro Plan: Enterprise Plan.
-
OAuth scope:
auditlogs:read. -
Role: Company Admin in your Miro organization.
💡 Not on Enterprise Plan yet? Upgrade to Miro Enterprise to unlock audit logs and gain comprehensive visibility into your team's activities in Microsoft Sentinel.
For detailed instructions, refer to the documentation.
Tables Ingested
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
MiroAuditLogs_CL |
? | ✓ | ? |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Permissions
Resource Provider Permissions: - Workspace (Workspace): Read and Write permissions are required.
Custom Permissions: - Miro Enterprise Plan: Miro Enterprise Plan subscription is required. - Miro OAuth Application: Miro OAuth application with auditlogs:read scope and Company Admin role is required.
Setup Instructions
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
Step 1: Verify your Miro plan
- Ensure your organization has an active Miro Enterprise Plan.
- If you need to upgrade, contact Miro Sales or your account manager.
- You must be a Company Admin to set up this integration.
Step 2: Choose your setup option
There are two ways to set up the Miro Audit Logs connector.
Option 1 (recommended): Use Enterprise integrations - Simplest setup with automatic token generation. - Recommended for most users. - See Option 1 below.
Option 2 (alternative): Create custom OAuth application - More control over OAuth app configuration. - For advanced users or custom integration needs. - See Option 2 below.
Note: When using Option 1, the integration is automatically tied to the team with the largest number of users in your organization. When using Option 2, you can choose which team to install the app to. However, the team selection does not affect which logs are collected—both options provide organization-wide log access. All integration-relevant events from all teams are included in your logs.
Option 1: Enterprise integrations (recommended)
- Open Miro Company Settings.
- Expand the Apps and integrations section.
- Click Enterprise integrations.
- Enable the SIEM toggle.
- Copy the Access Token value that appears.
- Important: Store the token securely—it provides full access to audit logs.
- The token will work until you disable the toggle.
- Proceed to Step 3.
Option 2: Custom OAuth application (alternative)
- Go to Miro App Settings.
- Click Create new app.
- Select Non-expiring access token option during app creation.
- Enable the OAuth scope:
auditlogs:read. - Click Install app and get OAuth token.
- Authorize the app to access your organization.
- Copy the Access Token that is displayed.
- Important: Store the token securely—it provides full access to audit logs.
- The token will work until you uninstall the app.
Step 3: Learn more
For detailed information about Miro audit logs: - Miro Audit Logs documentation - Miro API reference - OAuth non-expiring tokens - Enterprise integrations settings
6. Connect to Miro to start collecting audit logs in Microsoft Sentinel.
Step 4: Connect to Miro
Provide your Miro access token below to complete the connection. - Access token: (password field) - Click 'Connect' to establish connection
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊